I think we have to thing about lowering the number of element on OSD tab. There are just too many settings and page takes very long to load. Maybe if we spliy OSD into 2 separate ones? Like "OSD Layout" and "OSD Settings" ?
What do you think about that?

I think we have to thing about lowering the number of element on OSD tab. There are just too many settings and page takes very long to load. Maybe if we spliy OSD into 2 separate ones? Like "OSD Layout" and "OSD Settings" ? What do you think about that?

Would the idea be to move the items on the right side to its own tab?

What about if the sections were collapsable? That could look neater.

Just collapsing the sections probably wouldn't make it load faster.
I am leaning on merging this one and addressing the split/load time on a subsequent pull request.

Something like this.

We can probably leave the video format and settings on the osd layout tab

And move alarms and the rest to the other tab, and possibly rename it to Advanced OSD settings, or something along those lines.

I guess so long as it doesn’t change anything on the layout. It could go in a different tab. But, that would only be about 10 things. I don’t think that would increase the load time by a great deal.

I will merge this one for now, while we investigate how to make the osd tab faster

Its interesting to notice the OSD page load time, based on the FC processor clock speed I assume... The H743 or F765 generally load within 10s.. While the F722 and then F405 is a little slower. But the F411 takes 35s or so... It teaches me patience.

One thing I would like to do is investigate the loading process of the osd tab.

We may be able to cut the cpu usage on the fc and number of calls (and time to load) if we can:

1. Get list of visible elements
2. Only query the state of visible elements (hopefully, in bulk, async to fool the user the loading is fast)

Current implementation seems to go through the whole list and send it in a bulk reply. It does not appear to be doing much processing though, so I am not sure if the above would be faster.